Ping @narimiran

version-1-6 is dead, baby. version-1-6 is dead.

I'm not sure about dead quite yet. OpenBSD 7.7 was just released yesterday and the only Nim package provided is 1.6.18. I tried compiling Nim 2.2.4 from source on amd64 OpenBSD 7.7 and I ran into minor compilation issues where openbsd wasn't mentioned in a when-case and koch tools failed when compiling nimble because it used posix_fallocate but I was successful after making some minor patches so this made me hopeful to see 2.2 available for a package in the next 7.8 release.

I ran testament all and got, what I think is, a decent score: FAILURE! total: 517 passed: 501 skipped: 12 failed: 4

the only Nim package provided is 1.6.18

This means they not using even the latest released 1.6 version — 1.6.20.

If we merge this (and before that, we need to update our CIs in the version-1-6 branch, and who knows what more), why do you think they'll switch to some random unreleased commit? (There are no plans of another 1.6.x release.)

I tried compiling Nim 2.2.4 from source on amd64 OpenBSD 7.7 and I ran into minor compilation issues

1. Is Nim 2.0.16 any better?
2. Can you report/fix those issues in devel, and we can then backport them to version-2-2?

This means they not using even the latest released 1.6 version — 1.6.20.

Right, I'll request for that to be updated. It was 1.6.18 for the last OpenBSD release too.

There are no plans of another 1.6.x release.

Understood. Not a problem to skip this merge. I can submit a patch to the OpenBSD package that can add it to 1.6.20. There are already four patches as it is:
build.sh
config/nim.cfg
dist/nimble/src/nimblepkg/options.nim
lib/pure/asyncnet.nim

1. Is Nim 2.0.16 any better?

Nim 2.0.16 took the exact same patches to allow compiling of tools and got testament all result of:
FAILURE! total: 101 passed: 36 skipped: 0 failed: 65

2. Can you report/fix those issues in devel, and we can then backport them to version-2-2?

Yes. issue #24922 and pull #24923
and nimble pull request already being merged.

try later, if needed, if you get 500 error from the cvsweb openbsd server. they must be getting slammed from the new release
or use github mirror https://github.com/openbsd/ports/tree/master/lang/nim/patches

I'll request for that to be updated

If we can fix stuff in devel on our side (like you did in #24923 — thanks!), then it might be wiser to do that first (is there something else that needs to be done?) and then propose to OpenBSD to update to Nim 2.2.6 (currently unreleased, of course, but once released it will contain all the fixes needed).